Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm developing an app using Titanium Appcelerator.
It's a simple flashcards app for iOS which allows users to scroll through a selection of foreign words, and view the equivalent english translation on 'the other side' of the card (flip transition!). Each card has an audio link and there are a few options for the user to choose also.
I would like to know if anyone reccommends the use of the alloy framework?
Does it speed up the development time?
Are there any use cases where alloy would not be appropriate?
I think your app is definitely appropriate for alloy, the same things appropriate for Titanium in general work with Alloy. One of the key things to think about is that using Alloy will not necessarily speed up development time. That is not the goal, the goal is to separate the concerns (Model View Controller), and provide cross-platform and multiple form factor support. If you are interested purely in speed of development stick with regular Titanium.
However, where it can speed up dev time is in your persistence strategy, sql integration of models is built in with Alloy. So, if this flashcard app your thinking of creating has the users creating flashcards on their phone, then using them later, I would definitely go with Alloy to take advantage of the model stuff.
Take note that the documentation is kind of sparse, I ported an existing clients project to Alloy and really had to find my own way on a lot of things, but It was not a simple app.
Essentially, if you want to 1) Release to multiple platforms and form factors and not have migraines, 2) Have a built-in easy to use persistence strategy, 3) Be able to maintain your code at a later date, or have other people look at it and be able to tell whats going on, then I would definitely use Alloy.
Here are some links that will help you to know more about alloy framework,
1 Official appcelerator doc
2 A presentation on Alloy framework
3 Google group : Appc Ti Alloy
4 appcelerator / alloy in github
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
The community reviewed whether to reopen this question 1 year ago and left it closed:
Original close reason(s) were not resolved
Improve this question
I would like to start a mobile app with VueJS. Can anyone please suggest which Framework I can choose between vue-native or nativescript-vue?
Vue-Native is nothing but a wrapper around ReactNative. So the question becomes ReactNative vs NativeScript?
In my opinion, it's NativeScript.
Supports frameworks like Angular & Vue
Works with Core JavaScript / TypeScript too
Better code sharing
100% access to native apis
ReactNative got a huge community and range of plugins, but the problem beings when you want to customise. Every app is unique in it's own way, it becomes really hard to customise a plugin for your own needs at least until you have good exposure to Objective C / Java and handle your own forks etc.,
With NativeScript you can always access the native objects & apis form JavaScript, simply write overrides on plugins within your project if you want to customise anything.
Here are few blog posts & videos those compare these frameworks.
Would Airbnb Have Fared Better With NativeScript Instead of React Native?
ReactNative vs NativeScript
As #Manoj mentioned about the biggest advantage of using Nativescript is : You can access all the native elements and apis from Javascript.
I think another plus is the ability to create a code-sharing project. New Vue CLI plugin enables code sharing between web and mobile.There’s nothing quite as awesome as watching your web, iOS and Android app all spinning up at once with the same codebase.
You can further read on nativescript blog and here is the sample project.
You should also look into simply wrapping your Vue app with Cordova. I was required recently to build a mobile app and went through both vue-native & nativescript-vue, eventually ending up with Cordova.
At a basic level, you can wrap any static website and compile it as an android or ios app. If you need native elements you can also do so once Cordova fires the 'deviceready' event.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm working fully in Xamarin Classic iOS and Android. But I tried Xamarin.Forms since past 2 months. It's very hard for me to create UI. I don't know that is just me or someone else is also facing. I know there is some library like Xamarin-Labs,etc... Also there is custom renderer. But if I have to create custom rendered even in so called Cross - Platform (don't hate me, I'm in love with Xamarin) then it is pitty thing. Also it is taking so much time to create simple UI(This is because I'm new to it), but is there any way to create things easy for developers with Xamarin.Forms? I saw there are lots of app created with Xamarin.Forms with actually cool and complex UI. It is very easy to create app with Classic Xamarin. The only problem I'm facing is code sharing. So guys please help me with Xamarin.Forms, is it good for any production application(with complex ui, I know Xamarin doesn't suggest it for complex UI, but I know the dev community.) So need you help to sharper my blade with Xamarin.Forms.
You know Xamarin forms is not intended to do complex UI, for complex UI You must use Xamarin.iOS/Android, nevertheless if this is not the question here are some tutorials for simply and beautiful UI:
https://www.syntaxismyui.com/category/xamarin-forms/inanger-xamarin-forms/
http://blog.twintechs.com/advanced-xamarin-forms-techniques-for-flexible-and-performant-cross-platform-apps-part-5-page-in-page-embedding
And If you don't like to code UI and want to spend money then:
http://grialkit.com/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Apple's announcement of the 'Optimized for iOS7' mandate is as follows:
https://developer.apple.com/news/index.php?id=12172013a
Starting February 1, new apps and app updates submitted to the App Store must be built with the latest version of Xcode 5 and must be optimized for iOS 7. Learn more about preparing your apps by reviewing the iOS Human Interface Guidelines.
There's been several questions regarding this already regarding the Xcode part, which seems fairly straight-forward (use Xcode 5!)
But the 'optimized for' part along with the HIGs is much more vague.
It appears that some interpret this to mean "It has to look like a native iOS7 app...Helvetica Thin, extremely flat icons, translucency, etc"
But I find that hard to accept given how broad app UIs tend to be. I don't see EA Sports changing all their UIs to match, for example. Has apple published any clarifying documentation in regards to what they mean by 'optimized for' and how closely the UI must adhere to iOS7 conventions and to what range of apps this would apply to (all apps? Only native apps? HTML5 apps? Games? etc.)?
Coming from someone who has submitted a lot of apps, this isn't something I would see Apple enforcing unless you stray very far from the iOS 7 look and feel.
For example, I could imagine someone trying to submit an application that looks & feels a lot like an iOS 6 app, which is something they wouldn't want (confusing). Or, imagine somebody creating a new UIDatePicker that looks like the iOS 6 date picker (confusing). They're simply looking for consistency.
So, rule of thumb when it comes to HIG--use what apple provides. For custom views, respect the platform and don't confuse the user.
More specifics https://developer.apple.com/appstore/resources/approval/guidelines.html
One current completely unsupported working hypothesis seems to be that, as of Feb 1st, an iOS app has to be built with the iOS 7 as Base SDK, and that the newer iOS 7 metrics can't break anything in the UI (as in non-operable buttons or alerts, views partially-hidden under the status bar or behind tool bars, text half off-screen, etc.), and the app can't attempt to call any deprecated APIs removed from iOS 7.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I have learned basics of ExtJS and developed some web apps using ExtJS. Now I have to develop web desktop using ExtJS (like desktop app which is present in examples folder) but I am not able to find any documentation or tutorial or book about how to develop it.
Does anyone knows how to develop web desktop application using ExtJS 4? Where can I get any tutorial/ book/ video about developing web desktop?
I doubt you'll find a book or tutorial dedicated to exactly what you're looking for, but you can put together enough resources across the internet to do the trick.
A Google search of "extjs 4 cookbook" turned up a book called "Ext JS 4 Web Application Development Cookbook" that seems to have plenty of information. However, it seems very new and I personally haven't read it, so I can't vouch for it. But it's there.
Other than that, Sencha's own documentation site will have most of what you need. The series of articles on App Architecture may be of some use if you're planning to take the MVC approach, as will the articles on components and layouts.
That will cover the basics, but there's no real definitive guide to making a web desktop app that I'm aware of. It all depends on what your requirements are, how much time you have available, etc. If you're looking for help with a specific component (like creating a Windows-style file browser system) then you'll probably have better luck asking more narrow questions.
You can just use default Web Desktop Sample provided by Sencha and modify it a little bit.
I am also interested in, I did what I advice you, so you can look what I have received now:
http://www.bdovhan.orgfree.com/
Hmmm, these free hosting providers use lot of ads if your site becomes clickable.
I created another mirror, there should be no ads: http://www.julfysoft.16mb.com/index.html
but it can take a while to load it...
We inspired from the desktop sample and we build a full functional web app using Extj 6.7 along with Unigui Framework (Delphi), and the result is awsome:
Just implementing the idea step by step.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I inherited an old app, written in C#/.NET 2.0. (un)Luckily there was no documentation - not even comments. So as I'm adding enhancements to the application based on new requirements I'm also building a mental model of what the app does and how it does it - architecture in other words.
I was wondering what tools exist out there to "deconstruct" the app and go from raw code to something higher level? The app's not really heavy in OO - in fact one of the objects used is called a "function". It's mostly just a bunch of methods - a lot methods that seem to jump out of nowhere.
I want to translate the raw code to some sort of requirements doc stating what the app does and how it executes. What's the best way to do it? Are there any apps out there that can help me? Maybe templates of what I should/should not include? Maybe books/sites that you recommend? The goal is to provide documentation for me and for future developers maintaining the app.
Personally, I would start with Robert C Martin's Agile book, and Eric Evan's book on Domain Driven Design. Those are theory books, but Uncle Bob's book specifically talks about revamping code to be manageable, just like your situation.
It's pretty essential to layer your software so you can start to remove dependencies, which will make everything very simple and easy to maintain.
I am a database guy, so I started with a good ORM like Entity Framework or Fluent NHibernate. I prefer websites, so I went with ASP.NET's MVC 2, then started writing all the parts of those books, namely a data Repository, Services to pull data and Control to push it. MVC is a very nice separation of data concerns and "View" concerns which are your screens. Before long, you would have very clean and easily maintained software.
If you are using VS 2010, you can see a menu with the name: Architecture. Using this tool, you can create a dependency graph of your application, you can use it as described in the following:
Link