StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11545076
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-18T15:37:46.847
FavoriteCount
0
LastActivityDate
2012-07-18T15:37:46.847
LastEditDate
LastEditorUserId
0
OwnerUserId
1299462
ParentId
11542435
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
While Titanium can technically be a "write once, deploy everywhere" platform, I think it is best for a developer to create the same codebase for each platform while slightly altering the development to suit the specific target platform. For instance, the needs you have while targeting Android devices (with ranges anywhere from high-end smartphones like the Galaxy Nexus to tablets like the Nexus 7) differ greatly from needs that are best-practices for iOS applications. I wouldn't want the exact same application being targeted for members of the same device family even. Take iOS for example - the most well-designed applications for both iPhone and iPad have strong UI/UX differences that should be accounted for due to their greatly different look-and-feel and use. A good example of an application that does not adhere to the "write once, deploy everywhere" model is the Wunderlist application developed by 6wunderkinder. While they used Titanium to develop their iOS application, they did not use Titanium also for their Android app, and instead decided to drop Titanium completely and develop natively. This is not to say that you can't stick with Titanium for both platforms (I have made applications on both iOS and Android adapted from the same code), but it was a completely understandable choice that the 6wunderkinder team decided to make. While it would have been fairly easy for them to use much of their existing iOS Titanium codebase for their Android application, there were likely many sacrifices that they would have had to make in order for it to be displayed the way they envisioned it on Android. So yes, if going for a great-looking application (getting it exactly the way you want it on both device families) it is often a great deal of code that you have to change. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs targeting additional platforms in titanium just a matter of UI changes?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USbad
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.